Backup

Backup

When the system parameter BRURI is non-null, user changes are automatically backed up to the file ext_96xxdata.txt (where ext is the value of NVPHONEXT) on the HTTP server to a user-specified directory. Backup formats are as follows:

Table 9: Backup File Formats
Item/Data Value	Format
Generic	name=value
Contacts	ABKNAMEmmm=ENTRY_NAME ABKNUMBERmmm=ENTRY_NUMBER_1 (where mmm is the one-, two-, or three-digit entry ID, with leading zeros for single and double-digit entry IDs)
User-generated Call Appearance labels with button identifiers of mm (the one- or two-digit button number of the entry with a lead zero for single-digit numbers)	PHNLABELmm=CAUSERLABEL
User-generated telephone Feature Button labels with button identifiers of mm (the one- or two-digit button number of the entry with a lead zero for single-digit numbers)	PHNLABELmm=FBUSERLABEL
User-generated SBM24 Call Appearance or Feature Button labels with button identifiers of mm (the one- or two-digit button number of the entry with a lead zero for single-digit numbers)	SBMLABELmm=CAUSERLABEL or FBUSERLABEL, as applicable

In addition to the parameters listed in Table 7, a backup saves the options and non-password parameters shown in Table 10.

Table 10: Options and Non-Password Parameters Saved During Backup
Parameter Name	Setting
LOGACTIVE	Call Log Active
LOGBRIDGED	Log Bridged Calls
OPTAGCHAND	Handset Automatic Gain Control
OPTAGCHEAD	Headset Automatic Gain Control
OPTAGCSPKR	Speaker Automatic Gain Control
OPTAUDIOPATH	Audio Path
OPTCLICKS	Button Clicks
OPTERRORTONE	Error Tones
PERSONALRING	Personalized Ring
PHNREDIAL	Redial
PHNSCRONCALL	Go to Phone Screen on Calling
PHNSCRONALERT	Go to Phone Screen on Ringing
PHNTIMERS	Call Timer
PHNVISUALALERT	Visual Alerting